999 Exception Code

The Global Exclusion code, also referred to as the 999 exception code, allows GIS Geographic Information System. A computer application that involves storing and manipulating electronic maps and related data. Also, mapping software combining spatial information about where places and events are located with data attributes describing those places and events. Data Hub to completely ignore any features or records with this code upon ingest.

As a result, that means features and/or records assigned this code are:

  1. Not quality controlled.

  2. Not included in any GIS Data Hub exports.

  3. Not provisioned to any SI Spatial Interface or ECRF Emergency Call Routing Function. Receives location information (either civic address or geo-coordinates) as input and uses this information to provide a URI that can be used to route an emergency call toward the appropriate PSAP for the caller’s location. Depending on the identity and credentials of the entity requesting the routing information, the response might identify the PSAP, or an Emergency Services Routing Proxy (ESRP) that acts on behalf of the PSAP to provide final routing to the PSAP itself. The same database that is used to route a call to the correct PSAP might also be used to subsequently route the call to the correct responder, e.g., to support selective transfer capabilities. process.

  4. Are ignored during the ingest process.

Note: If a Global Exclusion (999) exception code is applied to a feature, then that feature is omitted from all quality control (QC Quality Control) checks, except for the Exception Code Formatting QC check, and will therefore not yield any QC check fallouts other than Exception Code Formatting fallouts.

 

GIS Data Hub allows users to map one layer from the source data into multiple layers in the data target.

For example, if an agency’s Exchange layer included both exchange and tandem information, the user could layer and field map that singular source Exchange layer into a Tandem layer and an Exchange layer in the data target, creating two layers from the original singular source layer.

When this functionality is used, the Global Exception (999) code is applied in an on/off manner. If any of these layers contain a 999 code and exception codes are configured for a single layer in the data target, then those 999 features are removed from all resulting layers in the data target, even if their exception code field in the Layer and Field Mapping page was not field mapped.

How does this work? If a user wants to apply exception codes to one of these data target layers, but not the other(s), the user can accomplish this by uploading a copy of the selected source layer for each of the data target layers they would like to create from it.

Using the example above, users would complete the following.

  1. Submit their Exchange layer in their source data.

  2. Submit a copy of the Exchange layer to be layer and field mapped into their Tandem layer.

    The copy can be named whatever the user chooses, so long as it complies with GIS Data Hub naming convention parameters.

With this done, users could then apply the Global Exclusion exception code of 999 to, for example, the Exchange layer, while not using the Global Exclusion exception code at all on the Tandem layer.